You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comprehensive documentation update for Joomla version 54-60
Added 25+ new feature descriptions with usage examples
Included PR references and impact assessments
Structured migration guides for breaking changes
Diagram Walkthrough
flowchart LR
A["Original Documentation"] --> B["Enhanced Documentation"]
B --> C["XML Field Extensions"]
B --> D["Date/DateTime Fields"]
B --> E["Plugin Improvements"]
B --> F["Batch Processing"]
B --> G["API Enhancements"]
B --> H["Migration Guides"]
Loading
File Walkthrough
Relevant files
Documentation
new-features.md
Comprehensive new features documentation expansion
migrations/54-60/new-features.md
Added detailed documentation for 25+ new features
Included usage examples and code snippets for each feature
Added PR references and impact assessments
Structured content with consistent formatting and migration guides
Verify that feature names, API/class references, and PR links match upstream changes (e.g., AdminModel stdClass change, Adapter removals, WebAsset usage) to avoid propagating incorrect guidance.
## Admin model returns stdClass instead of CMSObject-**PR**: [#42961](https://github.com/joomla/joomla-cms/pull/42961) by **laoneo**-**Usage migration**:
```php
// Before
$item->get('catid');
// Now
$item->catid;
Impact: Code calling get() on AdminModel items must switch to property access.
</details>
<details><summary><a href='https://github.com/joomla/Manual/pull/507/files#diff-1759a8daad05cbac620d11e5edc6057eec7cbca0e149d12aaac323445446bb53R29-R318'><strong>Consistency</strong></a>
Ensure uniform wording and formatting for sections (Usage, Impact, Migration) and validate that all code snippets have matching opening/closing tags and accurate types (e.g., field types date/time/datetime).
</summary>
```markdown
## New Date and Datetime fields
- **PR**: [#37456](https://github.com/joomla/joomla-cms/pull/37456) by **Fedik**
- **What changed**: Introduced `date` and `datetime` field types.
- **Usage**:
```xml
<field type="date" name="date"/>
<field type="time" name="time" filter="SERVER_UTC"/>
<field type="datetime" name="datetime" filter="USER_UTC"/>
Impact: Developers can rely on HTML5 input controls instead of JS widgets.
Fix language autoload in CMSPlugin constructor to work safely
Clarify that property existence and nullability may differ when switching from get() to direct access, and show a guarded example. This prevents runtime notices for missing properties in extensions following this guide.
## Admin model returns stdClass instead of CMSObject
- **PR**: [#42961](https://github.com/joomla/joomla-cms/pull/42961) by **laoneo**
- **Usage migration**:
```php
// Before
$item->get('catid');
// Now
$item->catid;
- ``` -- **Impact**: Code calling `get()` on AdminModel items must switch to property access.+ // Safe access example+ $catid = property_exists($item, 'catid') ? $item->catid : null;+ ```+- **Impact**: Code calling `get()` on AdminModel items must switch to property access. Ensure you handle missing properties to avoid notices.+
Apply / Chat
Suggestion importance[1-10]: 7
__
Why: This suggestion significantly improves the migration guide by providing a safe access example, which helps developers avoid potential runtime errors when migrating their code.
Medium
Document required dialog markup
Add a note that the data-joomla-dialog attribute requires the dialog markup or target to exist and that legacy data-toggle="modal" is no longer honored here. This prevents broken links when migrating templates.
## Use Dialog for Article links when “modal option” is selected
- **PR**: [#42461](https://github.com/joomla/joomla-cms/pull/42461) by **Fedik**
- **What changed**: Article links with modal option now use Joomla’s Dialog system.
- **Usage**:
```html
+ <!-- Ensure the target/dialog exists -->+ <div id="popup" hidden data-joomla-dialog-content>+ <h3>Popup</h3>+ <p>Content...</p>+ </div>
<a href="#popup" data-joomla-dialog='{"textHeader":"Popup"}'>Open</a>
- ``` -- **Impact**: Consistent UI, templates relying on Bootstrap modals must adapt.+ ```+- **Impact**: Consistent UI, templates relying on Bootstrap modals must adapt. Legacy `data-toggle="modal"` is not applied; migrate to `data-joomla-dialog` with proper dialog markup.
Apply / Chat
Suggestion importance[1-10]: 7
__
Why: The suggestion improves the documentation by providing a complete and functional example, which prevents confusion and helps developers correctly implement the new dialog system.
Medium
Align description with example
The example introduces a time field but the heading and "What changed" mention only date and datetime. Either include time in the description or remove the time line to avoid confusion. Align the "What changed" text with the actual usage snippet.
-## New Date and Datetime fields+## New Date, Time and Datetime fields
- **PR**: [#37456](https://github.com/joomla/joomla-cms/pull/37456) by **Fedik**
-- **What changed**: Introduced `date` and `datetime` field types. +- **What changed**: Introduced `date`, `time`, and `datetime` field types.
- **Usage**:
```xml
<field type="date" name="date"/>
<field type="time" name="time" filter="SERVER_UTC"/>
<field type="datetime" name="datetime" filter="USER_UTC"/>
Impact: Developers can rely on HTML5 input controls instead of JS widgets.
- [ ] **Apply / Chat** <!-- /improve --apply_suggestion=2 -->
<details><summary>Suggestion importance[1-10]: 5</summary>
__
Why: The suggestion correctly identifies a mismatch between the documentation's title/description and the code example, improving clarity and accuracy.
</details></details></td><td align=center>Low
</td></tr>
<tr><td align="center" colspan="2">
- [ ] More <!-- /improve --more_suggestions=true -->
</td><td></td></tr></tbody></table>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Type
Documentation
Description
Comprehensive documentation update for Joomla version 54-60
Added 25+ new feature descriptions with usage examples
Included PR references and impact assessments
Structured migration guides for breaking changes
Diagram Walkthrough
File Walkthrough
new-features.md
Comprehensive new features documentation expansionmigrations/54-60/new-features.md